Method and apparatus for transceiving data for multimedia transmission system

ABSTRACT

A method and an apparatus for transmitting data in a multimedia transmission system are provided. The method includes receiving, from an encapsulation function layer, a second data unit having one or more first data units, configuring payload header information, the payload header information including a payload type and configuration information, by analyzing header information of the second data unit, configuring one or more payloads from the second data unit based on sizes of the one or more first data units, configuring a multimedia data packet by combining payload header information corresponding to each of the one or more payloads, and transmitting the multimedia data packet to a counterpart entity. Each of the one or more payload includes at least one payload element, the type of which is selected from among a first type, a second type, a third type, a fourth type, and a fifth type.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a continuation application of prior application Ser.No. 14/397,055, filed on Oct. 24, 2014, which is a U.S. National Stageapplication under 35 U.S.C. § 371 of an International application filedon Apr. 25, 2013 and assigned application number PCT/KR2013/003582,which claimed the benefit of a U.S. Provisional application filed onApr. 25, 2012 in the U.S. Patent and Trademark Office and assigned Ser.No. 61/638,048, the entire disclosure of each of which is herebyincorporated by reference

TECHNICAL FIELD

The present disclosure relates to a multimedia transmission system. Moreparticularly, the present disclosure relates to a method and apparatusfor transmitting and receiving multimedia data.

BACKGROUND

The term ‘multimedia service’ may refer to call services such as VideoCall, streaming services such as Video on Demand (VOD) service, and/orservices such as Multicast and Broadcast Service. Real-time multimediaservices may be divided into call services, interactive services andstreaming services depending on the service type, and may also bedivided into unicast, multicast and broadcast depending on the number ofparticipating users.

A related-art broadcast network usually uses Moving Picture ExpertsGroup (MPEG)-2 Transport Stream (MPEG-2 TS), for transmission ofmultimedia content. MPEG-2 TS is used as a typical transmissiontechnology for transmitting a bit stream, with which multiple broadcastprograms and/or multiple coded video bit streams are multiplexed, in anerror-ridden transmission environment. MPEG-2 TS is suitable for use indigital TV broadcasting or the like in the multimedia age.

MPEG-2 TS may have a few limitations in supporting multimedia services.In other words, MPEG-2 TS may have limitations such as one-waycommunication, inefficiency of transmission due to a fixed frame size,and unnecessary overhead which occurs when data is transmitted using thetransport protocol and Internet Protocol (IP) that are specific toaudio/video.

Therefore, MPEG has proposed an MPEG Media Transport (MMT) standard asone of the multimedia transmission technologies for supportingmultimedia services based on the MPEG technology. For example, the MMTstandard may be applied to efficiently transmit hybrid content over aheterogeneous network. The term ‘hybrid content’ as used herein mayrefer to a collection of content having multimedia elementscorresponding to video/audio/applications. The heterogeneous network maybe, for example, a network in which a broadcasting network and a mobilecommunication network coexist.

The MMT standard aims at defining an IP-friendly transmission technologywhich is the basic technology in a transmission network for multimediaservices. To this end, there is a need for a structure of an MMTtransport packet for more efficiently delivering logical data objects ina variety of formats, including coded media data, in a changingmultimedia service environment.

Other aspects, advantages, and salient features of the disclosure willbecome apparent to those skilled in the art from the following detaileddescription, which, taken in conjunction with the annexed drawings,discloses various embodiments of the present disclosure.

SUMMARY

Aspects of the present disclosure are to address at least theabove-mentioned problems and/or disadvantages and to provide at leastthe advantages described below. Accordingly, an aspect of the presentdisclosure is to provide a method and apparatus for efficientlytransmitting and receiving coded media data in a multimedia transmissionsystem.

Another aspect of the present disclosure is to provide a method andapparatus for transmitting and receiving logical data objects in avariety of formats in a multimedia transmission system.

Another aspect of the present disclosure is to provide a method andapparatus for configuring a heterogeneous multimedia data packet in abroadcasting system that supports multimedia services based on anInternet Protocol (IP), such as an IP address.

In accordance with an aspect of the present disclosure, a method fortransmitting data in a multimedia transmission system is provided. Themethod includes receiving, from an encapsulation function layer, asecond data unit having one or more first data units, configuringpayload header information, the payload header information including apayload type and configuration information by analyzing headerinformation of the second data unit, configuring one or more payloadsfrom the second data unit based on sizes of the one or more first dataunits, configuring a multimedia data packet by combining payload headerinformation corresponding to each of the one or more payloads, andtransmitting the multimedia data packet to a counterpart entity, whereineach of the one or more payloads includes at least one payload elementcorresponding to any one of a first type including one of the one ormore first data units, a second type including header information of oneof the one or more first data units, a third type including headerinformation of one of the one or more first data units and part of dataor only part of data, a fourth type including header information of thesecond data unit, and a fifth type including the entirety of the seconddata unit.

In accordance with another aspect of the present disclosure, a methodfor receiving data in a multimedia transmission system is provided. Themethod includes receiving, from a counterpart entity, a multimedia datapacket having a payload and payload header information including apayload type and configuration information, and detecting, from themultimedia data packet, one or more first data units generated by anencapsulation function layer and at least a part of a second data unithaving the one or more first data units, wherein the payload includes atleast one payload element corresponding to any one of a first typeincluding one of the one or more first data units, a second typeincluding header information of one of the one or more first data units,a third type including header information of one of the one or morefirst data units and part of data or only part of data, a fourth typeincluding header information of the second data unit, and a fifth typeincluding the entirety of the second data unit.

In accordance with another aspect of the present disclosure, anapparatus for transmitting data in a multimedia transmission system isprovided. The apparatus includes a data generation unit configured tooutput a second data unit having one or more first data units, a dataconfiguration unit configured to configure payload header information,the payload header information including a payload type andconfiguration information by analyzing header information of the seconddata unit, to configure one or more payloads from the second data unitbased on sizes of the one or more first data units, and to configure amultimedia data packet by combining payload header informationcorresponding to each of the one or more payloads, and a datatransmission unit configured to transmit the multimedia data packet to acounterpart entity, wherein the one or more payloads includes at leastone payload element corresponding to any one of a first type includingone of the one or more first data units, a second type including headerinformation of one of the one or more first data units, a third typeincluding header information of one of the one or more first data unitsand part of data or only part of data, a fourth type including headerinformation of the second data unit, and a fifth type including theentirety of the second data unit.

In accordance with yet another aspect of the present disclosure, anapparatus for receiving data in a multimedia transmission system isprovided. The apparatus includes a reception unit configured to receive,from a counterpart entity, a multimedia data packet having a payload andpayload header information including a payload type and configurationinformation, and an interpretation unit configured to detect, from themultimedia data packet, one or more first data units generated by anencapsulation function layer and at least a part of a second data unithaving the one or more first data units, wherein the payload may includeat least one payload element corresponding to any one of a first typeincluding one of the one or more first data units, a second typeincluding header information of one of the one or more first data units,a third type including header information of one of the one or morefirst data units and part of data, or only part of data, a fourth typeincluding header information of the second data unit, and a fifth typeincluding the entirety of the second data unit.

Other aspects, advantages, and salient features of the disclosure willbecome apparent to those skilled in the art from the following detaileddescription, which, taken in conjunction with the annexed drawings,discloses various embodiments of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects, features, and advantages of certainembodiments of the present disclosure will be more apparent from thefollowing description taken in conjunction with the accompanyingdrawings, in which:

FIG. 1 illustrates a hierarchical structure of an MPEG Media Transport(MMT) system according to an embodiment of the present disclosure.

FIG. 2 illustrates a structure of an MMT payload according to anembodiment of the present disclosure.

FIG. 3 illustrates a logical structure of an MMT package according to anembodiment of the present disclosure.

FIG. 4 illustrates a flowchart for configuring and transmitting amultimedia data packet including an MMT payload in an MMT systemaccording to an embodiment of the present disclosure.

FIG. 5 illustrates an operation of generating a multimedia data packetaccording to an embodiment of the present disclosure.

Throughout the drawings, it should be noted that like reference numbersare used to depict the same or similar elements, features, andstructures.

DETAILED DESCRIPTION

The following description with reference to the accompanying drawings isprovided to assist in a comprehensive understanding of variousembodiments of the present disclosure as defined by the claims and theirequivalents. It includes various specific details to assist in thatunderstanding but these are to be regarded as merely exemplary.Accordingly, those of ordinary skill in the art will recognize thatvarious changes and modifications of the various embodiments describedherein can be made without departing from the scope and spirit of thepresent disclosure. In addition, descriptions of well-known functionsand constructions may be omitted for clarity and conciseness.

The terms and words used in the following description and claims are notlimited to the bibliographical meanings, but, are merely used by theinventor to enable a clear and consistent understanding of the presentdisclosure. Accordingly, it should be apparent to those skilled in theart that the following description of various embodiments of the presentdisclosure is provided for illustration purpose only and not for thepurpose of limiting the present disclosure as defined by the appendedclaims and their equivalents.

It is to be understood that the singular forms “a,” “an,” and “the”include plural referents unless the context clearly dictates otherwise.Thus, for example, reference to “a component surface” includes referenceto one or more of such surfaces.

A hierarchical structure defined in the Motion Picture Experts Group(MPEG) Media Transport (MMT) standard will be described herein below.Various embodiments of the present disclosure provide the structure of amultimedia data packet. To this end, a detailed description will be madeof layers for generating a multimedia data packet in the hierarchicalstructure defined in the MMT standard. The term ‘multimedia data packet’as used herein may refer to a delivery frame for an MMT service.

An MMT Protocol (MMTP) defines an application layer protocol fordelivering a delivery frame configured in an MMT Payload Format (PF)over an Internet Protocol (IP) network. An MMT payload is designed to beefficiently delivered by being configured in an MMT payload format. Toefficiently deliver MPEG media data over heterogeneous IP networks, MMTdefines encapsulation formats, delivery protocols, and signaling messageformats.

FIG. 1 illustrates a hierarchical structure of an MMT system accordingto an embodiment of the present disclosure.

Referring to FIG. 1, shown are a media coding layer 110, anencapsulation function layer (Layer E) 120, a delivery function layer(Layer D) 130, a transport protocol layer 140, an Internet Protocol (IP)layer 150, and a control function layer (Layer C) 100, which are forconfiguring a multimedia data packet and transmitting the configuredmultimedia data packet.

In accordance with an embodiment of the present disclosure, the mediacoding layer 110 and the encapsulation function layer 120 may operate asa multimedia data generation unit for generating multimedia data that isbased on multimedia content and/or multimedia services. The deliveryfunction layer 130 may operate as a multimedia data configuration unitfor configuring a multimedia data packet based on the multimedia datareceived from the multimedia data generation unit. The delivery functionlayer 130 corresponding to the multimedia data configuration unit mayconfigure header information by identifying at least one multimedia dataprovided from the multimedia data generation unit, and may configure amultimedia data packet by combining the header information with theleast one multimedia data.

The multimedia data, which may be compressed in the media coding layer110, may be packetized in a form similar to a file format by theencapsulation function layer 120. The encapsulation function layer 120may generate data segments, which are small units for an MMT service, byreceiving the coded media data provided from the media coding layer 110or the stored media data, and may generate access units for an MMTservice using the data segments. The encapsulation function layer 120may generate a packet format for generation and/or storage andtransmission of hybrid content by combining and/or dividing the accessunits.

The delivery function layer 130 may convert at least one data unitoutput from the encapsulation function layer 120 into an MMT payloadformat and then may add an MMT transport packet header thereto toconfigure an MMT transport packet, or may configure a Real-Time Protocol(RTP) packet using an RTP which is the existing transport protocol.

The packets configured in the delivery function layer 130 may be finallyIP-packetized in the IP layer 150 after undergoing configuration by thetransport protocol layer 140, such as User Datagram Protocol (UDP) orTransport Control Protocol (TCP). The transport protocol layer 140 andthe IP layer 150 may operate as a data transmission unit. The controlfunction layer 100, which is optional, may generate control informationor signaling information used for transmission of data, may add thegenerated information to data, may transmit the data, and/or maytransmit the data through a separate signaling means.

An MMT payload format generated in the delivery function layer 130 maydefine a logical structure of at least one media unit to be delivered,by means of the MMT protocol or the RTP. An MMT payload may be specifiedby a payload format for delivering the encapsulated data unit or otherinformation by MMT layer protocols or other existing applicationtransport protocols. The MMT payload may provide information aboutstreaming and information about file transfer. In streaming, a data unitmay be an MMT Media Fragment Unit (MFU) or an MMT Processing Unit (MPU).In file transfer, a data unit may be an MMT asset and an MMT package.

FIG. 2 illustrates a structure of an MMT payload according to anembodiment of the present disclosure.

Referring to FIG. 2, an MMT payload 200 may be configured to include atleast one of at least one MMT MFU 210, at least one MMT MPU 220, atleast one MMT asset 230, and at least one MMT package 240.

The MFU 210 may be a common container format including coded media data,which is independent of any media codec, and can be independentlyprocessed by a media decoder. The MFU 210, which represents part ofsegmented data of the MPU 220, may be the minimum unit that can bedecoded independently. As an example, if coding is performed by usingone frame as an access unit, the MFU 210 may be one video frame. Inanother case, the MFU 210 may be one slice included in one frame.

The MPU 220, which is a container format including one or more MFUs andadditional delivery and processing-related information, may include avariety of numbers of MFUs generated from a plurality of differentaccess units. The MPU 220, which may be a coded media data unit that canbe completely and independently processed by an MMT compliant entity,may have a specific size, e.g., one Group of Picture (GOP) in the caseof video, depending on the application environment. As an example, theMPU 220 may have and/or may consist of a plurality of picture framesconstituting one GOP, e.g., a 1 second video, and the MFU 210 mayinclude each picture frame.

The MMT asset 230, which is a data entity having one or more MPUs, maybe the largest data unit, to which the same composition information andtransport characteristics are applied. The MMT asset 230 may includeonly one type of data, including packaged or multiplexed data. Forexample, at least a part of an Elementary Stream (ES) of audio, at leasta part of an ES of video, at least a part of an MPEG-UI (User Interface)widget package, at least a part of an MPEG-2 TS, at least a part of anMPEG-4 (MP4) file, and all or at least a part of an MMT package may eachbe an MMT asset 230.

The ES, which is defined by a specific media codec, may be logically oneor more MMT assets. The MMT asset 230 supporting a layered codec and amulti-view codec may overlap with other MMT assets.

MMT Composition Information (MMT-CI) may be the information defining aspatial and temporal relationship of MMT assets, and MMT TransportCharacteristics (MMT-TC) may define Quality of Service (QoS) needed fordelivery of MMT assets. An MMT-TC may be expressed as an Asset DeliveryCharacteristic (ADC), for a specific delivery environment.

The MMT package 240 may be defined as a collection of coded media dataand its related information, which are processed by an MMT compliantentity.

FIG. 3 illustrates a logical structure of an MMT package according to anembodiment of the present disclosure.

Referring to FIG. 3, an MMT package 300 may have, and/or consist of, atleast one MMT asset 320, MMT composition information 310, and at leastone ADC 330 representing at least one MMT transport characteristic. TheMMT package 300, which may be similar to the MMT package 240 illustratedin FIG. 2, may include description information such as an identifier,and locations of the MMT assets 320, and the MMT assets 320 in the MMTpackage 300 may be multiplexed and/or concatenated.

The MMT package 300 may be processed in units of MPUs, and the MMT asset320 may be a collection of one or more MPUs having the same MMT assetID. The transport characteristics related to each MMT asset 320 may beexpressed by the ADC 330. The ADC 330 may be used, by an entity ofand/or for packetizing an MMT package, to configure parameters of an MMTpayload and below-described header information of an MMT packet.

Among the logical entities that can be included in the MMT package, theMPU may include header fields that are based on the given definition andsome of these fields may be used for processing the MPU. In a case wherethe outer parts of the boundaries of MFUs in a payload of MPUs are cutoff, if the packet is lost, an error may be propagated longer. In mediadata requiring a low delay, an MFU needs to be immediately transmittedat the time of its generation. In this case, to prevent the transmissiondelay, the transmission order may be determined to transmit header fieldinformation of the MPU after transmitting the generated MFU data.

Given the above characteristics, an MMT payload should be configured tomaintain compatibility between MPU packets and MFU packets.

FIG. 4 illustrates a flowchart for configuring and transmitting amultimedia data packet including an MMT payload in an MMT systemaccording to an embodiment of the present disclosure. The operationsshown in FIG. 4 may be performed by the delivery function layer 130 fromamong the layers in FIG. 1.

Referring to FIG. 4, in operation 410, the delivery function layer 130may receive multimedia data provided from the encapsulation functionlayer 120. The encapsulation function layer 120 may provide multimediadata used to configure a multimedia data packet, and information relatedto each multimedia data.

In operation 420, the delivery function layer 130 may configure headerinformation, such as payload header information, related to an MMTpayload of the multimedia data packet based on the header information ofthe multimedia data. As an example, the payload header information mayprovide a length of an MMT payload, a type of payload data, informationrelated to fragmentation and aggregation, and any other similar and/orsuitable type of information that may be included in the payload headerinformation, and the payload header format may be defined by the systemoperator or the protocol standard.

In operation 430, the delivery function layer 130 may generate a payloadof a multimedia data packet for delivery of multimedia data, or in otherwords, the delivery function layer 130 may configure an MMT payload bycombining at least a part of the multimedia data received in operation410 with the header information configured in operation 420 in order togenerate an MMT packet.

In operation 440, an MMT packet, such as the MMT packet generatedaccording to operation 430, which is a multimedia data packet includingthe MMT payload, may be may be transmitted to a counterpart entity,e.g., a receiver, through a given transport protocol.

A description will now be made of a detailed procedure for configuring amultimedia data packet by a delivery function layer in charge oftransmission of multimedia data for MMT services, which is proposed inan embodiment of the present disclosure, and also made of and/oraccording to a payload format. Specifically, a transport data structurethat is based on the type of the data generated in the encapsulationfunction layer 120 may be provided. For configuration of a multimediadata packet, payload header information to be recorded in a headerregion and multimedia data to be recorded in a payload region may begenerated according to a given format.

FIG. 5 illustrates an operation of generating a multimedia data packetaccording to an embodiment of the present disclosure.

Referring to FIG. 5, an MPU file 510 may be data that the encapsulationfunction layer desires to transmit, and an MPU/MFU building block 520has a data structure for configuring transmission data. The MPU file 510may include header information 512 such as a File Type (FTYP) boxindicating a type of a file, an MMPU box indicating a structure of anMPU, an MOOV box indicating codec setting information, and MovieFragment (MOOF) box; and an MDAT box 514 having Video Samples (VSs) 516and MMT Hint Samples (HSs) 518. The MMPU box indicates that a type ofthe data stored in the MDAT box is MPU, and the MOOV box containsinformation about a media frame stored in the MDAT box. The MPU/MFUbuilding block 520 may include MPU metadata 522 such as FTYP, MMPU, MOOVand MOOF, and MFUs 524 having related HSs 526 and VSs 528.

An MMT payload may be configured based on the MPU/MFU building block520, and carried or transmitted in an MMT packet.

A procedure for configuring an MMT payload may be as follows.

A data configuration unit may analyze data 510 in the form of an MPUfile, which is provided from a data generation unit and desired to betransmitted, to determine type information, configuration information ofan MPU, setting information of a codec, starting point and size and/orlength information of data, from the header information 512 of the MPUdata 510. The data configuration unit may analyze the structure of MFUs516, such as the MFUs corresponding to VSs in FIG. 5, and MFU HSs 518constituting the MPU data 510, to determine an MFU header containing thesize, mutual importance and interconnection information of each MFU suchas information on the length or the like, and MFU data which is actualmedia data, and may also analyze the size of each MFU through the MFU HS518 indicating the starting offset and length of each MFU.

Based on the analyzed MPU format, the MPU/MFU building block 520 forconfiguring a transport packet may be configured. The MFU HS 518 may bean MFU header of the MPU/MFU building block 520.

The data configuration unit may configure each MFU as a transport unitbased on the size of each MFU, which is analyzed from the MFU HS 518. Inthis case, depending on the size of the MFU, at least one payload may beconfigured. The first, middle or last portion of each payload may beindicated by start_end_indicator, which is optional bits. The MPUmetadata 522 may also be treated as one configuration unit of theMPU/MFU building block 520.

The data type of each payload element may be presented as follows:

i. The MPU metadata 522 which may indicate a type of one payload, havingat least one of FTYP, MMPU, MOOV, MOOF and MDAT, is called MPU_Partial() and may be configured to include only the MPU header;

ii. If one MFU is configured as one payload, the type of the payload iscalled MFU_set( );

iii. In a case where one MFU is configured as multiple payloads, thetype of each payload is MFU_Partial( ) if the MFU includes only the MFUheader, and the type of each payload is MFU_chunk( ) if the MFU includesan MFU header and part of the MFU data, or includes part of the MFUdata;

iv. MPU_Partial( ) may indicate the type of a payload that includes onlythe MPU header; and

v. MPU_Set( ) may indicate the type of a payload that completelyincludes an MPU.

Shown below is syntax of an MMT payload according to an embodiment ofthe present disclosure. The below MMT payload format may be used for UDPtransport, exchange of point-to-point chunks, and transport of files.

   MMT_Payload( ) {    bit(N) type;    bit(N) asset_id;    switch (type){    case 0:       //configuration;       if (asset_id==0) {      //package configuration data       } else {       //assetconfiguration data       }       break;    case 1:       MFU_Partial( );      break;    case 2:       MFU_chunk( );       break;    case 3:      MFU_set ( );       break;    case 4:       MPU_Partial( );      break;    case 5:       MPU_Set( );       break; ...    }

As described above, an MMT payload may include a type field indicating adata type of the payload, and an asset_id indicating an identifier of anasset to which the payload, such as the MPU and/or the MFU, belongs. Theasset_id may exist to multiplex an MMT bit stream. The asset_id may beomitted if the MMT payload is delivered through, i.e. via, RTP and asingle asset is used.

Depending on the type field, the following various cases of elements maybe included in the MMT payload.

Case 0 may be used if the MMT payload contains configuration data of thedata to be transmitted. If asset_id=0, the MMT payload may includepackage configuration data. Otherwise, asset configuration data may beincluded.

An MFU_Partial( ) element corresponding to case 1 may be used when theMMT payload carries configuration data, such as header information, ofthe MFU data. An MFU_chunk( ) element corresponding to case 2 may beused when the MMT payload contains part of the MFU data together withconfiguration data, such as the header information, of the MFU data, orcarries all or part of the MFU data. An MFU_set( ) element correspondingto case 3 may be used when the MMT payload contains all of the MFU data,including the header and the data. An MPU_Partial( ) elementcorresponding to case 4 may be used when the MMT payload contains dataof the MPU. An MPU_Set( ) element corresponding to case 5 may be usedwhen the MMT payload contains all of the MPU data, including the headerand the data.

Additionally, the MMT payload may further include other units such as afile unit, signaling information of the control layer, and a protectionmessage.

MFU_Partial( ) may be defined to be a set of all of headers that areadded to a start of payload bytes and defined in the MFU, when the sizeof the MFU exceeds the size of the Maximum Transmission Unit (MTU).

MFU_chunk( ) may be defined to be a middle or a last part of a payloadof the MFU for the headers transmitted in the MFU_Partial( ) packets.

MFU_set( ) may be defined to be a packet that includes a predeterminednumber of complete MFUs.

MPU_Partial( ) may be defined to be a set of all of headers that areadded to the additional MFU_set element that is added to the optionalMFU_Partial( ) element, and that are defined in the MPU. Thepresence/absence of the additional elements may be determined dependingon the remaining bytes and the MFU length of the packet.

A description will now be made of examples of the MPU and MFU elements,together with the mapping between the MMT payload format and the MMTtransport packet. A description of the parameter fields that are knownin the art or that have nothing to do with various embodiments of thepresent disclosure will be omitted herein, but it should be noted thatsuch parameter fields do not limit the scope of the present disclosure.

The following represents an example of an MFU element.

mmt_mfu_element( ) {    ...    optional bit(2) start_end_indicator;   optional bit(1) rap_fragment_indicator;    optional bit(N)layer_dependency_info;    optional bit(N) scrambling_key_index;   payload( ); }

In the above example, start_end_indicator may be optional bitsindicating that the payload is a start, middle or end of an MFU.Additionally, start_end_indicator may indicate that the MFU includesRandom Access Point (RAP) data, and may include optimal bits indicatinga start and/or end position where the data is to be decoded, andrap_fragment_indicator may be optional bits indicting an address of astart point of the data that can be directly decoded, if the payloadcontains a start point of the randomly accessible data.

Also, scrambling_key_index may contain information about a series ofvalues capable of decrypting encryption, if the payload is encrypted.

Furthermore, layer_dependency_info may be information indicating thedependency between picture layers. Additionally, it may further includelayer identifiers (LayerIDs), a dependency count, signal rolling keys,similar to a MPEG-2 TS packet, and the like.

The following represents an example of an MPU element.

   mmt_mpu_element(multiple, timing)    {       optional bit(2)start_end_indicator;       bit (1) multiple_mfu_flag;       bit (1)no_mfu       bit (1) timing_flag;       bit(1) codec_update_flag;      bit(1) event_list_flag;       bit(1) clock_map;       bit(1)headers_first;       bit(1) multiple_aus_flag;       if(codec_update_flag) {          bit(16) codec_config_size;         bytes(codec_config_size) codec_config_data;          bit(8)downcouter ;//processing delay (remove)       }       if(event_list_flag) {          bit(16) num_events;          for (i=0;i<num_events; i++) {          ... //eventdata          }       }      if (multiple_mfu_flag) {          bit(N) num_MFUs;       } else {         num_MFUs = 1;          headers_first = 0;         multiple_aus_flag = 0;       }       if (timing_flag) {         optional bit(timestamps_bits) base_timestamp;          if(clock_map) {             bit(64) clock_ref          }          optionalbit(ts_inc_bits) ts_increment;          optional bit(2) constant_flag ;         optional bit(N) interval ;          if (ts_inc_factor)ts_increment *= ts_inc_factor;       }       for (i=0; i<num_MFUs; i++){          optional bit(N) decode_order_number;          if (timing &&(!i || multiple_aus_flag) ) {             optional bit(N) dts_diff;            optional bit(N)             composition_timestamp_offset;            mfu_dts = base_timestamp +             dts_diff *ts_increment;             mfu_cts   =   base_timestamp +composition_timestamp_offset * ts_increment;          }          if(multiple_mfu_flag)             optional bit(N) mfu_size;          if(!headers_first) mmt_mfu_element( );       }       if (headers_first) {         for (i=0; i<num_MFUs; i++) {             mmt_mfu_element( );         }       }    }

In the above example, start_end_indicator may be optional bitsindicating that the payload is a start, middle or end of an MPU, andmultiple_mfu_flag may be set to ‘1’ if the MPU has multiple MFUs. Also,no_mfu may be set to ‘1’ if no MFU is included in the MPU data like inthe case of file transfer.

Additionally, timing_flag may be used to correct the time stamp byindicating whether the current MFU belongs to the same access unit asthe previous one if the previous packet is lost, codec_update_flag maybe set to ‘1’ if the payload has codec configuration information,header_first may be set to ‘1’ if the payload starts at the headerinformation of the media data, and event_list_flag may be set if thepayload has an event list to be represented for the user. The event listmay list events belonging to the content.

Also, multiple_aus_flag may be set to ‘1’ if the payload containsmultiple frames. If a codec such as Advanced Audio Coding (AAC) is used,units for in-band codec configuration may be included in the MPUelement.

Furthermore, codec_update_flag may include codec_config_size indicatingthe size of codec configuration information and codec_config_dataindicating the codec configuration information. According to anembodiment of the present disclosure, if a codec is changed based on thecodec configuration information or if the codec configurationinformation is modified, at the beginning or in the middle of themultimedia streaming service, the presence/absence of the informationmay be set through the codec_update_flag. Also, downcounter may be usedto indicate that a few more payloads containing the codec configurationinformation exist after the current payload, if the codec configurationinformation is divided into multiple payloads. As an example, if thecodec configuration information is divided into multiple segments anddowncounter is set to ‘3’, a receiver may determine that payloads havingdowncounters of 2, 1 and 0 are later used to complete the codecconfiguration information. Upon receiving a payload of downcounter 0,the receiver may determine that the transmission of all payloads relatedto the codec configuration information is completed.

If event_list_flag is set, an event list to be delivered through atransmission unit may exist, and the event list may include num_eventsindicating the number of events and at least one event data. Accordingto an embodiment of the present disclosure, if the event data that hasalready been transmitted is used, the event may be expressed byincluding only the event identifier ‘event ID’ instead of the eventdata. According to an embodiment of the present disclosure, event datamay be transmitted in advance using a predetermined transport meansbefore transmission of the payload. Listed events may be executed afterbeing synchronized with the display of the frame. According to anembodiment of the present disclosure, audio may be optionally changedthrough the event list during playback of video data.

If multiple_mfu_flag is set, num_MFUs indicating how many MFUs thepayload has may exist in the MPU element. If multiple_mfu_flag is notset, num_MFUs is set to ‘1’, and header_first and multiple_aus_flag areset to ‘0’. According to an embodiment of the present disclosure, if amultimedia data unit desired to be transmitted has multiple frames, ormultiple slices in a single frame, the information for setting thenumber of multiple entities may be set.

If timing_flag is set, timing information for units in the MPU may beincluded in the MPU element.

Additionally, as many MFUs as num_MFUs may be listed in the MPU element.Since the order of MFUs may be different from the order of decoderinputs, decode_order_number may indicate the order that the MFU is inputto the decoder and may be optionally included.

If multiple_mfu_flag is set to ‘1’, mfu_size indicating the size of eachMFU may be further included. In the present disclosure, it is assumedthat the MFUs that are input to the data configuration unit have thesame size.

If headers_first is not set to ‘1’, one mmt_mfu_element( ) may beincluded.

If headers_first is set to ‘1’, as many mmt_mfu_element( ) as num_MFUsmay be included in the MPU element.

The receiver, which may be a physical element, unit, and/or device,configured in accordance with an embodiment of the present disclosuremay include a reception unit configured to receive a multimedia datapacket from a counterpart entity, and an interpretation unit configuredto extract and interpret at least one MFU or MPU included in themultimedia data packet or at least a part thereof depending on theabove-described format of the MMT payload.

According to an embodiment of the present disclosure, at least one ofthe data generation unit, the data configuration unit, the datatransmission unit, the receiver, the reception unit, and theinterpretation unit may include at least one hardware element. It can beseen that the methods and operations of the various embodiments of thepresent disclosure can be implemented in the form of hardware, software,or a combination of hardware and software. Such an arbitrary softwaremay be stored in, for example, irrespective of being erasable orrewritable, a volatile or non-volatile storage device such as aRead-Only Memory (ROM), a memory such as a Random Access Memory (RAM), amemory chip device, a processor, a computer chip, Erasable ProgrammableROM (EPROM), an Integrated Circuit (IC), an optically or magneticallyrecordable and a machine readable, e.g., a computer readable, storagemedium such as a Compact Disc (CD), a Digital Versatile Disc (DVD), amagnetic disk, or a magnetic tape. It can be also appreciated that thememory included in the mobile terminal is one example ofmachine-readable devices suitable for storing a program includinginstructions that are executed by a processor device to therebyimplement various embodiments of the present disclosure. Accordingly,the present disclosure may include a program including a code forimplementing a device and a method described in an arbitrary claim ofthe present specification, and a machine readable, e.g., a computerreadable, storage medium storing such a program. Furthermore, such aprogram may be electronically transferred through an arbitrary mediumsuch as a communication signal transferred through a wired or wirelessconnection, and the present disclosure may appropriately includeequivalents thereof.

The above-described format of the MMT payload may enable the efficientdelivery and aggregation/fragmentation of MPUs and MFUs.

While the present disclosure has been shown and described with referenceto various embodiments thereof, it will be understood by those skilledin the art that various changes in form and details may be made thereinwithout departing from the spirit and scope of the present disclosure asdefined by the appended claims and their equivalents.

What is claimed is:
 1. A method for receiving media content in amultimedia system, the method comprising: receiving one or moremultimedia data packets generated based on a data unit, the data unitbeing fragmented into at least one sub data unit, each multimedia datapacket including a packet header and a payload; and decoding the one ormore multimedia data packets to recover the media content, wherein eachof the one or more multimedia data packets comprise type informationindicating whether a respective payload data included in a payload of agiven multimedia data packet comprises either a metadata of the dataunit or a data element derived from the at least one sub data unit,wherein the type information comprises a first value indicating that therespective payload data comprises the metadata of the data unit if therespective payload data comprises the metadata of the data unit, andwherein the type information comprises a second value indicating thatthe respective payload data comprises the data element derived from theat least one sub data unit if the respective payload data comprises thedata element derived from the at least one sub data unit.
 2. The methodof claim 1, wherein the metadata of the data unit comprises informationregarding configuration of the at least one sub data unit.
 3. The methodof claim 1, wherein the metadata of the data unit comprises a box havingcodec configuration information.
 4. The method of claim 1, wherein thetype information is included in the packet header of the respectivemultimedia data packet.
 5. The method of claim 1, wherein the payload ofthe given multimedia data packet further comprises a fragmentationindicator indicating that the payload is one of a set including a start,a middle or an end of the data unit.
 6. The method of claim 1, whereinthe metadata of the data unit comprises one of file type information ofthe data unit, movie fragment metadata of the data unit or a motionpicture experts group (MPEG) media transport (MMT) processing unit(MMPU) box being placed after the file type information to provideinformation regarding to the data unit.
 7. The method of claim 1,wherein the respective multimedia data packet comprises informationidentifying an asset to which the payload data included in therespective multimedia data packet belongs.